All GitHub workflows were cancelled due to failure one of the required jobs.
Failed workflow url: https://github.com/paritytech/polkadot-sdk/actions/runs/18556622090
Failed job name: test-linux-stable

gh issue view 8944 --json state,title

Yes, I think is a better approach. We can just query the state and ensure is OPEN

something like

if [[ $(gh issue view 1243 --json state  &>1 | jq -r .state) == "OPEN" ]];then echo pass; else echo err;fi

thanks @DenzelPenzel / @lrubasze 🙌

I think test zombienet-polkadot-smoke-0003-deregister-register-validator needs to have an issue, otherwise the job will be failing:
https://github.com/paritytech/polkadot-sdk/blob/150e8b399afb81cd466a6837d0f5587b62b32fd0/.github/zombienet-flaky-tests#L2C1-L2C60

LGTM

Just noticed that PR numbers are treated like issue numbers. See this:

❯ gh issue view 10034 --json state,title,url,id,stateReason,number
{
  "id": "PR_kwDOKDT1Ss6t-Z9p",
  "number": 10034,
  "state": "OPEN",
  "stateReason": "",
  "title": "feat: add validation for zombienet flaky tests",
  "url": "https://github.com/paritytech/polkadot-sdk/pull/10034"
}

vs

❯ gh issue view 9980 --json state,title,url,id,stateReason,number
{
  "id": "I_kwDOKDT1Ss7QkIP6",
  "number": 9980,
  "state": "OPEN",
  "stateReason": "",
  "title": "Fix zombienet-polkadot-functional-0014-chunk-fetching-network-compatibility",
  "url": "https://github.com/paritytech/polkadot-sdk/issues/9980"
}

Not sure. Maybe we could just ignore it. Alternatively we could detect it it by checking the url or id in order to distinguish if it is an issue or not.

Yes, I think from GH point of view are two variant (issue/pr) and the number will not be repeated. We should add a regex to check the url is for an issue. 👍

Thx!